On 2/23/24 16:01, mf wrote:
> [...]
> A new run is started unless:
> [...]
> - the tuc file is identical to the one of the previous run
Hi Massi,
many thanks for your reply.
If ConTeXt relies on that condition to stop compilation, then it would
be great to know how it is performed to invoke
On 2/23/24 23:58, Bruce Horrocks wrote:
>> On 23 Feb 2024, at 13:32, Pablo Rodriguez via ntg-context
>> wrote:
>> [...]
>> Is there any way to check if compilation needs any other run?
>> [...]
> Rather than use the wrapup() hook can why not rename the file using
> a second job on the command
os.remove(exists_pdf) end
>os.rename(pdf_file_name, ("%s_%s-%s.pdf"):format(c_r, tex.jobname,
> sha_pdf))
> end
> )
> \stopluacode
> \stoptext
>
> In short, it adds its SHA256 to the final filename.
>
> Since renames the PDF document in each run, I
rmat(c_r, tex.jobname,
sha_pdf))
end
)
\stopluacode
\stoptext
In short, it adds its SHA256 to the final filename.
Since renames the PDF document in each run, I would like to remove the
output from the previous run.
The table seems not to store the value from a previous run.
I see now that I am c
t adds its SHA256 to the final filename.
Since renames the PDF document in each run, I would like to remove the
output from the previous run.
The table seems not to store the value from a previous run.
I see now that I am creating it again with each run.
Is there any way to check if compilat
On 8/28/21 1:17 AM, Hans Hagen via ntg-context wrote:
> On 8/27/2021 8:53 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> How can I get that match for #1 ends in the last slash (including it
>> "../a/b/cb/ce.b/ca.b/c/") and match for #2 ends in the last period
>> (excluding it, "dabc")?
>
On 8/27/21 10:56 PM, Tomas Hala via ntg-context wrote:
> Hi Pablo,
>
> is the following what you need?
>
> context("2a. " .. url:match "[^/]+/.+[.]") -- path and name with period
> context("2c. " .. (url:match "[^/]+[^.]+$") :match ".+[.]") -- name with
> period
Hi Tomáš,
well, I
On 8/27/2021 8:53 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\starttext
\startluacode
url = "../a/b/cb/ce.b/ca.b/c/dabc.pdf"
context(url)
context("0 ok. " .. url:match "^(.*).pdf$") -- name and path
context("1. " .. url:match
Hi Pablo,
is the following what you need?
context("1. " .. url:match ".+/")
context("2a. " .. url:match "[^/]+/.+[.]") -- path and name with period
--context("2b. " .. url:match "[^/]+[^.]+$") -- name with period and
extension
context("2c. " .. (url:match "[^/]+[^.]+$") :match
Dear list,
I have the following sample:
\starttext
\startluacode
url = "../a/b/cb/ce.b/ca.b/c/dabc.pdf"
context(url)
context("0 ok. " .. url:match "^(.*).pdf$") -- name and path
context("1. " .. url:match "^(.*).+$") -- path
context("2. " .. url:match"[^/]+[.$]") --
> Am 04.12.2020 um 10:04 schrieb Hans Hagen :
>
> On 12/4/2020 8:02 AM, Axel Kielhorn wrote:
>>> Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
>>> :
>>>
>>> The following example shows the output of all commands:
>>>
>>> \starttext
>>> \starttabulate [|T|T|]
>>> \NC \type{\jobname}
On 12/4/2020 8:02 AM, Axel Kielhorn wrote:
Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
:
The following example shows the output of all commands:
\starttext
\starttabulate [|T|T|]
\NC \type{\jobname} \NC \jobname \NC\NR
\NC \type{\jobfilename} \NC \jobfilename
> Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
> :
>
> The following example shows the output of all commands:
>
> \starttext
> \starttabulate [|T|T|]
> \NC \type{\jobname} \NC \jobname \NC\NR
> \NC \type{\jobfilename} \NC \jobfilename \NC\NR
> \NC
On 12/1/2020 6:55 PM, Otared Kavian wrote:
Hi Wolfgang,
Thank you for your explanations: I am wondering whether this kind of
information could go into the wiki, and if yes what would be an appropriate
title for that page (of course I'll do it).
However the two commands
\inputfilesuffix
Hi Wolfgang,
Thank you for your explanations: I am wondering whether this kind of
information could go into the wiki, and if yes what would be an appropriate
title for that page (of course I'll do it).
However the two commands
\inputfilesuffix
\jobfilesuffix
put inside the file « myfile.tex
Otared Kavian schrieb am 01.12.2020 um 18:10:
Thanks Hraban, this might be also useful and I'll keep it somewhere on my mind,
but for the project I was asking my question \jobname is enough.
Best regards: Otared
On 1 Dec 2020, at 17:33, Henning Hraban Ramm wrote:
Am 01.12.2020 um 16:20
Thanks Hraban, this might be also useful and I'll keep it somewhere on my mind,
but for the project I was asking my question \jobname is enough.
Best regards: Otared
> On 1 Dec 2020, at 17:33, Henning Hraban Ramm wrote:
>
>
>
>> Am 01.12.2020 um 16:20 schrieb Otared Kavian :
>>
>> Thanks
> Am 01.12.2020 um 16:20 schrieb Otared Kavian :
>
> Thanks Tomás! Indeed \jobname does the job :-)
In case you need the current component file in a project environment:
\currentcomponent
Hraban
___
If your
Thanks Tomás! Indeed \jobname does the job :-)
Best regards: Otared
> On 1 Dec 2020, at 15:25, Tomas Hala wrote:
>
> Hi Otared,
>
> try \jobname.
>
> Best wishes,
>
> Tomáš
>
>
> Tue, Dec 01, 2020 ve 02:45:18PM +0100 Otared Kavian napsal(a):
> # Hi everyone,
> #
> # I have to typeset a
Hi Otared,
try \jobname.
Best wishes,
Tomáš
Tue, Dec 01, 2020 ve 02:45:18PM +0100 Otared Kavian napsal(a):
# Hi everyone,
#
# I have to typeset a few files which get each an input file named in a certain
way. For instance, a file named « myfile.tex » in which another file named «
Hi everyone,
I have to typeset a few files which get each an input file named in a certain
way. For instance, a file named « myfile.tex » in which another file named «
myfile-buffer.tex » is used as an \input file, as in
% content of myfile.tex
%
\starttext
This is a test.
\input
Dear list,
I have this sample:
\setupinteraction[state=start]
\starttext
\def\cB{file.pdf}
\def\cC{file with spaces.pdf}
%~ \def\PathName{\cldcontext{[[\env{completepath}]]}}
\def\PathName{%
\cldcontext{string.gsub([[\env{completepath}]], "", "/")}}
no
On Thu, 21 May 2020, Hans Hagen wrote:
On 5/21/2020 10:43 AM, Aditya Mahajan wrote:
On Thu, 21 May 2020, Aditya Mahajan wrote:
Hi,
`context --purgeall filename` behaves differently from `context
--purgeall`.
`context --purgeall` deletes all files with the name `*-temp-*`. I would
have
On 5/21/2020 10:43 AM, Aditya Mahajan wrote:
On Thu, 21 May 2020, Aditya Mahajan wrote:
Hi,
`context --purgeall filename` behaves differently from `context
--purgeall`.
`context --purgeall` deletes all files with the name `*-temp-*`. I
would have thought that `context --purgeall filename
On Thu, 21 May 2020, Aditya Mahajan wrote:
Hi,
`context --purgeall filename` behaves differently from `context --purgeall`.
`context --purgeall` deletes all files with the name `*-temp-*`. I would have
thought that `context --purgeall filename` will delete all files with the
name `\jobname
Hi,
`context --purgeall filename` behaves differently from `context --purgeall`.
`context --purgeall` deletes all files with the name `*-temp-*`. I would have
thought that `context --purgeall filename` will delete all files with the name
`\jobname-temp-*` but it does not.
Is there a way
On 5/1/2013 11:31 AM, Romain Diss wrote:
Hi,
I just noticed a small bug in the log of a context job. It has no incidence
but maybe this can cause a side effect somewhere.
When a file contain several dot in its name, context remove the last part in
the result filename in the log:
$ context
Thanks, Thomas. This is good to have for many purposes. But, for the task
of generating PDFs of components that are part of a larger product, the
problem of cross-references is but one of several issues—especially if one
wants ConTeXt to do most (if not all) of the work.
Alan
On Sun, May 5,
Wolfgang: OK—but a clarification. Yes, that will give me the individual
component files, but not with the page numbers etc that they would have
when they are compiled as part of the product. What I am interested in is
the extraction of component files during the compilation of a larger
product
On 05/05/2013 02:27 PM, Alan Bowen wrote:
Wolfgang: OK—but a clarification. Yes, that will give me the individual
component files, but not with the page numbers etc that they would have
when they are compiled as part of the product.
http://pragma-ade.com/general/magazines/mag-1103.pdf
HTH
Wolfgang—
Can this be extended so as to allow the extraction of the individual
component files (as PDFs with their component names) when processing a
product file?
Alan
On Thu, May 2, 2013 at 2:44 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
Am 01.05.2013 um 23:02 schrieb
Am 04.05.2013 um 13:50 schrieb Alan Bowen bowenala...@gmail.com:
Wolfgang—
Can this be extended so as to allow the extraction of the individual
component files (as PDFs with their component names) when processing a
product file?
There is no need for such a feature because you can
Am 01.05.2013 um 23:02 schrieb Wolfgang Schuster schuster.wolfg...@gmail.com:
Am 01.05.2013 um 12:16 schrieb Alan BRASLAU alan.bras...@cea.fr:
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
Hi,
I just noticed a small bug in the log of a context job. It has no incidence
but maybe this can cause a side effect somewhere.
When a file contain several dot in its name, context remove the last part in
the result filename in the log:
$ context test.foo.bar
...
system files
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an external extraction of single pdf pages to separate
files.
However, is it
Alan wrote:
In the production of (scientific) articles for
journal submissions, one is often expected to
supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an external extraction of single pdf pages to separate
files.
It might
Am 01.05.2013 um 12:16 schrieb Alan BRASLAU alan.bras...@cea.fr:
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an
On Wed, 1 May 2013 16:16:07 +0200
Sietse Brouwer sbbrou...@gmail.com wrote:
Alan wrote:
In the production of (scientific) articles for
journal submissions, one is often expected to
supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
whitespace etc. Isn;t there a true verbatim that I can use on
a macro like \currentcomponent? Something along the lines of
\verbatimexpand{\currentcomponent}?
Untested: \filename{\currentcomponent}
Works. When outside a component (e.g. index) it defaults to the string 'text'.
Thanks,
G
Simple question, guys (and gals),
how do I get the filename (full path not needed) in the footer of my document?
I want it there while writing the book and remove it in the final stages. I am
using MKII (TeXLive 2011 still)
texexec --pdf --mode=editor --once ../products/prd_book.tex
TeXExec
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII
···date: 2013-01-20, Sunday···from: Gerben Wierda···
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing
On 20 Jan 2013, at 16:09, Philipp Gesang wrote:
···date: 2013-01-20, Sunday···from: Gerben Wierda···
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my
···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices, then the TeX command
\jobname is what you are looking
,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices
on a macro like \currentcomponent? Something along the lines of
\verbatimexpand{\currentcomponent}?
Untested: \filename{\currentcomponent}
Aditya
___
If your question is of interest to others as well, please add
On Sun, Dec 23, 2012 at 02:50:06PM +0100, Hans Hagen wrote:
On 12/23/2012 7:29 AM, Khaled Hosny wrote:
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets
On 12/23/2012 7:29 AM, Khaled Hosny wrote:
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets stripped. Anyway, after some
searching it turned out this was added
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets stripped. Anyway, after some
searching it turned out this was added in 2004 for ConTeXt to workaround
some MetaPost
be transparent to the rest of TeX.
MKIV on slackware Linux.
What error? the primitive \input has some special parsing properties
maybe adding \relax after the filename helps
-
Hans Hagen
On 2012-07-24 john Culleton j...@wexfordpress.com wrote:
Hi John,
\startstandardmakekup
\startstandardmakeup
I would recommend to use ConTeXts environment, component, product
mechanism. See wiki: project structure.
Marco
If I set up my main file thus:
\starttext
\input title.tex
\input copyright.tex
\startfrontmatter
\completecontent
\chapter{Introduction}
\stopfrontmatter
\startbodymatter
\input body.tex
\stopbodymatter
\startappendices
\stopappendices
\startbackmatter
\chapter{Index}
%\chapter{Acknowledgement}
if the filename has no special characters in it.
Can this be fixed?
Yeah, please fix this ASAP. I keep all my context files in a directory which
I call /dev/null, and for some reason, this doesn't really work. But I am
not going to change the name of my directory, no, you have to rewrite your
On 6-3-2011 9:36, Vnpenguin wrote:
/dev/null as folder name ? Wow, what a crazy idea !
well, \input /dev/null/thesis-chapter-1.tex
does miracles (in germany)
Hans
-
Hans Hagen | PRAGMA
Hi,
I have an image file with two dots: file.xy.pdf
I can embed this file with
\externalfigure[file.xy.pdf][][width=\textwidth]
When leaving out the extension, the image is not found, e.g.:
\externalfigure[file.xy][][width=\textwidth]
For the time being, I renamed the files but it would
Hi
Context fails to run with an input (filename or directoryname) that includes
special characters.
example files:
%%%
reviczky@arlequin ~/minimal % la
total 0
drwxrwxr-x 1 reviczky reviczky 60 2011-03-05 19:58 ./
drwxr-xr-x 1 reviczky reviczky 2148 2011-03-05 20:00 ../
drwxrwxr-x 1 reviczky
On Sat, 5 Mar 2011 20:09:12 +
Reviczky, Adam adam.revic...@kcl.ac.uk wrote:
It works with the + character though.
The same problem goes for the directory names;
directories with ~ in the name drops and error, even if
the filename has no special characters in it.
Can this be fixed
Yeah, please fix this ASAP. I keep all my context files in
a directory which I call /dev/null, and for some reason,
this doesn't really work. But I am not going to change the
name of my directory, no, you have to rewrite your
software!
Thomas
Dear Thomas
I understand, that it's not a good
On Sat, 5 Mar 2011 20:38:13 +
Reviczky, Adam adam.revic...@kcl.ac.uk wrote:
Dear Thomas
I understand, that it's not a good idea, and I've seen
similar issues on the list
(http://www.ntg.nl/pipermail/ntg-context/2010/052339.html).
I ran into this by making a deb package of a software
only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
A simple yes, can be done or no, its a really bad idea is perfectly enough
for me.
I'll think about a workaround outside context.
Cheers,
Adam
On Sat, 5 Mar 2011, Reviczky, Adam wrote:
only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
I'll think about a workaround outside context.
The error is with the backend.
luatex (and pdftex and even tex) do not like filenames
Reviczky, Adam adam.revic...@kcl.ac.uk writes:
only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
A simple yes, can be done or no, its a really bad idea is perfectly enough
for me.
See also section 1.7 on page 11 of the ConTeXt
Am Thu, 05 Nov 2009 17:28:08 -0330 schrieb Roger Mason:
Martin,
Martin Scholz mar...@scholz-net.org writes:
is there a way in conTeXt how I can use a filename, so that I can write
a text where I can refer to it for using it in the following scenario:
I need 4 documents with nearly
Hi Roger, List
Thanks that sounds ok, but now I need to know I can use this by an
external program, as I try to build a letter for Lx-Office, an OpenSource
ERP Programm that uses TeX for processing the output and I can not really
switch in it the type how it is called, so I need more or
Am Thu, 05 Nov 2009 22:18:54 +0100 schrieb Hans Hagen:
Hi Roger, List
Thanks that sounds ok, but now I need to know I can use this by an
external program, as I try to build a letter for Lx-Office, an
OpenSource ERP Programm that uses TeX for processing the output and I
can not really
On Thu, 5 Nov 2009, Martin Scholz wrote:
is there a way in conTeXt how I can use a filename, so that I can write a
text where I can refer to it for using it in the following scenario:
I need 4 documents with nearly the same content. what I like to do is to
switch in the document depending
Hello,
It seems, that one cannot use accented characters in file-names. Example:
context état.tex fails with:
This is LuaTeX, Version beta-0.40.1-2009051420 (Web2C 7.5.7)
\write18 enabled.
! I can't find file `./?at.tex'.
* ./état.tex
Please type another input file name:
Is it
Peter Münster wrote:
Hello,
It seems, that one cannot use accented characters in file-names. Example:
context état.tex fails with:
This is LuaTeX, Version beta-0.40.1-2009051420 (Web2C 7.5.7)
\write18 enabled.
! I can't find file `./?at.tex'.
* ./état.tex
Please
Many thanks,
Greetings
Thomas Lohmann
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Patrick Gundlach wrote:
Hello Hans,
Well, I don't think you can do this. You can only get the name of the
main TeX file by using \jobname, but thats all. (Hopefully I didn't
miss some secret.) Different approach: put some info in your file with
a macro like \define\thisfile{/path/to/test.tex}.
Hello Hans,
there is also \currentfile
\starttext
\currentfile
\stoptext
- undefined cs \currentfile
Patrick
--
texshow-web: http://members.ping.de:8061
ConTeXt wiki: http://members.ping.de:8062
___
ntg-context mailing list
[EMAIL PROTECTED]
Hello Thomas,
I'm looking for a comand to insert the current filename and or path like
inserting the current date with \currentdate. Any help?
Well, I don't think you can do this. You can only get the name of the
main TeX file by using \jobname, but thats all. (Hopefully I didn't
miss some
73 matches
Mail list logo
